The tEntryScreen object from TurboPower DEW (Data Entry Workshop) descends
from the standard OWL object tDlgWindow. Users asked me how to make
tEntryScreen work together with my object tDialogWindow from my DialogWn/Janus
unit. (tDialogWindow is a tWindow descendand that replaces Borlands tDialog and
tDlgWindow but descends from tWindow. This makes it easy to use tDialogWindows
as MDI child windows). Now here are the changes necessary to make tEntryScreen
work together with tDialogWindow:

1) add a 'Uses DialogWn'
2) make tEntryScreen descend from tDialogWindow instead of tDlgWindow (of course <g>)
3) disable the GetWindowClass and GetClassName methods: tDialogWindow retrieves
   the dialog class name directly from the resource and does it's own
   BorDlg/non-BorDlg/Ctl3D modifications ('Janus' property)

Changes apply to file "oodewcc.pas"

  Uses
    ...
{$IfDef Janus}
    DialogWn,
{$EndIf}

{$IfDef Janus}
  tEntryScreenParent = tDialogWindow;
{$Else}
  tEntryScreenParent = tDlgWindow;
{$EndIf}

  PEntryScreen = ^TEntryScreen;
  TEntryScreen = object(tEntryScreenParent) {Object corresponding to an entry screen}
...
{$IfNDef Janus}
    procedure GetWindowClass(var AWndClass : TWndClass); virtual;
    function  GetClassName : PChar; virtual;
{$EndIf}
...
  end;

  constructor TEntryScreen.Init(AParent : PWindowsObject;
                                ATitle : PChar; var Buffer);
    {-Initialize a TEntryScreen object}
  begin
    tEntryScreenParent.Init(AParent, ATitle);
    ...
  end;

{$IfNDef Janus}
  ... code for GetWindowClass and GetClassName
{$EndIf}


Peter Sawatzki, Buchenhof 3, D58091 Hagen, GERMANY
CIS: 100031,3002